Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Arachne algorithm from PrusaSlicer 2.9 #7819

Open
wants to merge 11 commits into
base: main
Choose a base branch
from

Conversation

Noisyfox
Copy link
Collaborator

See individual commits for change details

Noisyfox and others added 11 commits December 22, 2024 16:32
…oronoi vertex is inside a corner of a polygon.

Cherry-picked from prusa3d/PrusaSlicer@669c931

Co-authored-by: Lukáš Hejl <[email protected]>
…ator

Especially in cases when the object is composed only of 2 external perimeters and 1 or 2 internal perimeters, the order of perimeters wasn't optimal and differed from the Classic perimeter generator. That caused unnecessary long travels before the external contour was printed.

The ordering of perimeters is slightly inspired by the latest changes in CuraEngine.

Cherry-picked from prusa3d/PrusaSlicer@1087508

Co-authored-by: Lukáš Hejl <[email protected]>
…g for Arachne generator.

The previous implementation during the grouping of perimeters using depth-first searches unnecessarily searched nodes that had no impact on grouping, which significantly increased the search space.

Cherry-picked from prusa3d/PrusaSlicer@86309ba

Co-authored-by: Lukáš Hejl <[email protected]>
Cherry-picked from prusa3d/PrusaSlicer@919740f

Co-authored-by: Martin Šach <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant